Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 877e156cd9d56fb5cc78c1d18673ac0cd0314cf6f717117189f29322824c39b5

Tx prefix hash: 5d71ec65e8b99813495186a723600403d6866bc26e984b9ce5a56985261bdd6a
Tx public key: d47f080759412a11bb2f50441e046c85b9ba6a4188fb9ef6ec2201f5ea84daf1
Timestamp: 1716642130 Timestamp [UCT]: 2024-05-25 13:02:10 Age [y:d:h:m:s]: 00:298:10:25:00
Block: 1029728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213304 RingCT/type: yes/0
Extra: 01d47f080759412a11bb2f50441e046c85b9ba6a4188fb9ef6ec2201f5ea84daf102110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf58809f32d1e2fb388bdb74f1fc6d86eb68f97423e17d46d6bcc11f9c197c4f 0.600000000000 1497897 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": 1029738, "vin": [ { "gen": { "height": 1029728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf58809f32d1e2fb388bdb74f1fc6d86eb68f97423e17d46d6bcc11f9c197c4f" } } ], "extra": [ 1, 212, 127, 8, 7, 89, 65, 42, 17, 187, 47, 80, 68, 30, 4, 108, 133, 185, 186, 106, 65, 136, 251, 158, 246, 236, 34, 1, 245, 234, 132, 218, 241, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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