Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a94763416508a2df0cba2176f7682d94f2de45e2af0f263e51f31d844235b689

Tx prefix hash: 213405bb7d90573985026d67afedaed9925d0d424e86a89d677bc4a28e9bd267
Tx public key: 381e74244eab6caa8d5a4559a0fc8035a26fdeda1fbdb152daa8fe3a72671c6f
Timestamp: 1724035742 Timestamp [UCT]: 2024-08-19 02:49:02 Age [y:d:h:m:s]: 00:143:01:46:02
Block: 1091017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102339 RingCT/type: yes/0
Extra: 01381e74244eab6caa8d5a4559a0fc8035a26fdeda1fbdb152daa8fe3a72671c6f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fc57f3428b8b13bf73bb3ca1fd2446b366a865240e92cd10d30a6e7c20bac3f 0.600000000000 1565642 of 15

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": 1091027, "vin": [ { "gen": { "height": 1091017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fc57f3428b8b13bf73bb3ca1fd2446b366a865240e92cd10d30a6e7c20bac3f" } } ], "extra": [ 1, 56, 30, 116, 36, 78, 171, 108, 170, 141, 90, 69, 89, 160, 252, 128, 53, 162, 111, 222, 218, 31, 189, 177, 82, 218, 168, 254, 58, 114, 103, 28, 111, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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