Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40e2f50ec9aeda817ff30a57d49c1ef045d209ab91bee17a038cd14ca333b174

Tx prefix hash: aebf2dfaea091882e5fc38f962232d6f2386299af68c59a683980e44a07dc0b8
Tx public key: 3806c262590fce56d6d4a194e58895bd7cab08e0d36ca346b1976c3ec8ab2443
Timestamp: 1716385241 Timestamp [UCT]: 2024-05-22 13:40:41 Age [y:d:h:m:s]: 00:313:03:53:01
Block: 1027596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223815 RingCT/type: yes/0
Extra: 013806c262590fce56d6d4a194e58895bd7cab08e0d36ca346b1976c3ec8ab244302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4297b908a7164e96e56ab6c9529b9abae795e2f2dc0dc38985c69bbade7f6b44 0.600000000000 1495295 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": 1027606, "vin": [ { "gen": { "height": 1027596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4297b908a7164e96e56ab6c9529b9abae795e2f2dc0dc38985c69bbade7f6b44" } } ], "extra": [ 1, 56, 6, 194, 98, 89, 15, 206, 86, 214, 212, 161, 148, 229, 136, 149, 189, 124, 171, 8, 224, 211, 108, 163, 70, 177, 151, 108, 62, 200, 171, 36, 67, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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