Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f50e400da6693ac9da47fba418939f999cd408479c5c8c27d274d85f3ed3406a

Tx prefix hash: 8f2146fb97236171aa8826eaf834b7193613d0c3d5c4282c239b30e10db477cf
Tx public key: e7cf7833f1a1e91fbf9572638cbf4a5722db44f21e38599855b236dfad2f5809
Timestamp: 1648340829 Timestamp [UCT]: 2022-03-27 00:27:09 Age [y:d:h:m:s]: 03:083:16:11:06
Block: 467124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 839945 RingCT/type: yes/0
Extra: 01e7cf7833f1a1e91fbf9572638cbf4a5722db44f21e38599855b236dfad2f580902110000000a4a0f5013000000000000000000

1 output(s) for total of 17.386995002000 dcy

stealth address amount amount idx
00: c3578682b9d5a377e6f1d264e1044d0fdae28149680c07fd4cd6ddc036d9d0d7 17.386995002000 885571 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 467134, "vin": [ { "gen": { "height": 467124 } } ], "vout": [ { "amount": 17386995002, "target": { "key": "c3578682b9d5a377e6f1d264e1044d0fdae28149680c07fd4cd6ddc036d9d0d7" } } ], "extra": [ 1, 231, 207, 120, 51, 241, 161, 233, 31, 191, 149, 114, 99, 140, 191, 74, 87, 34, 219, 68, 242, 30, 56, 89, 152, 85, 178, 54, 223, 173, 47, 88, 9, 2, 17, 0, 0, 0, 10, 74, 15, 80, 19, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8