Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44a6e33c8956b8c9b6b83d9f09197a852030c7c99fea8c56b39d90fce8703963

Tx prefix hash: 429f7c814030e1260a245ba242f871f69156e57710bd9b603757ea9cd4090f33
Tx public key: cfb075faca86265a5621f529fa0355f12224e2e0231db466674b85fb7b0be82a
Timestamp: 1762034173 Timestamp [UCT]: 2025-11-01 21:56:13 Age [y:d:h:m:s]: 00:065:04:30:55
Block: 1402919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46673 RingCT/type: yes/0
Extra: 01cfb075faca86265a5621f529fa0355f12224e2e0231db466674b85fb7b0be82a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edd63e5e0a4d15b73a434a691c7884bd2abd7ce0845d84f71ba4378cde4161e8 0.600000000000 1891244 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": 1402929, "vin": [ { "gen": { "height": 1402919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edd63e5e0a4d15b73a434a691c7884bd2abd7ce0845d84f71ba4378cde4161e8" } } ], "extra": [ 1, 207, 176, 117, 250, 202, 134, 38, 90, 86, 33, 245, 41, 250, 3, 85, 241, 34, 36, 226, 224, 35, 29, 180, 102, 103, 75, 133, 251, 123, 11, 232, 42, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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