Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 940c315b4cf7a5fc744b54ffc7a8a6e9c6148e3f979911a29f27ab066485052d

Tx prefix hash: cc32a066b18dbb8df6da6c3f2defd524339557cf9ef9a4047e74263face398c1
Tx public key: 283f6a0842345a4476f020df962f4d2cc506d0845f3fce584aa4c0f192f4fb38
Timestamp: 1647883855 Timestamp [UCT]: 2022-03-21 17:30:55 Age [y:d:h:m:s]: 02:250:05:06:59
Block: 463387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 698320 RingCT/type: yes/0
Extra: 01283f6a0842345a4476f020df962f4d2cc506d0845f3fce584aa4c0f192f4fb38021100000001cb8520c2000000000000000000

1 output(s) for total of 17.889852796000 dcy

stealth address amount amount idx
00: f03eedb056513352709e718ac9c8ed81f934c97dd18d2f5c69d55a53dbceb268 17.889852796000 881040 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": 463397, "vin": [ { "gen": { "height": 463387 } } ], "vout": [ { "amount": 17889852796, "target": { "key": "f03eedb056513352709e718ac9c8ed81f934c97dd18d2f5c69d55a53dbceb268" } } ], "extra": [ 1, 40, 63, 106, 8, 66, 52, 90, 68, 118, 240, 32, 223, 150, 47, 77, 44, 197, 6, 208, 132, 95, 63, 206, 88, 74, 164, 192, 241, 146, 244, 251, 56, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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