Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e93093afdb991165c5cd4f69779ca7e2bc9f703a6f6d12d34f83c79ba0ae1bc6

Tx prefix hash: a7afaeac598e7fd773b4a4730cccb0d2b0060c9abbe92fd75694ee4af733ccef
Tx public key: 4e00d09656b51a96dbd4f5852022db7226a04b97d69e4195b3fa343fe56f361d
Timestamp: 1686330217 Timestamp [UCT]: 2023-06-09 17:03:37 Age [y:d:h:m:s]: 01:304:09:01:56
Block: 778672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478712 RingCT/type: yes/0
Extra: 014e00d09656b51a96dbd4f5852022db7226a04b97d69e4195b3fa343fe56f361d02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.614122841000 dcy

stealth address amount amount idx
00: 1160979885946df2b558044c67e5d76298aab4bd1a4b2dcebc0723cf28ec911c 1.614122841000 1228307 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": 778682, "vin": [ { "gen": { "height": 778672 } } ], "vout": [ { "amount": 1614122841, "target": { "key": "1160979885946df2b558044c67e5d76298aab4bd1a4b2dcebc0723cf28ec911c" } } ], "extra": [ 1, 78, 0, 208, 150, 86, 181, 26, 150, 219, 212, 245, 133, 32, 34, 219, 114, 38, 160, 75, 151, 214, 158, 65, 149, 179, 250, 52, 63, 229, 111, 54, 29, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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