Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a44b3a34efb0d7ad210adaa509590b958a7befbaf8f8b1be866412668924f38a

Tx prefix hash: fab51262b4deebc9c720af2538f1fc62369d627edba13871fa45958d69bd0b83
Tx public key: 1cbd42325e155914f5ef1c7e63ab5c4b654bc4175c2dd6fea5e76601a07dbafb
Timestamp: 1740690311 Timestamp [UCT]: 2025-02-27 21:05:11 Age [y:d:h:m:s]: 00:267:02:25:53
Block: 1228616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188664 RingCT/type: yes/0
Extra: 011cbd42325e155914f5ef1c7e63ab5c4b654bc4175c2dd6fea5e76601a07dbafb02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b85d83eae9c531f7c85000f17fc15119a18eb5d36a23ac7794e464fda9699624 0.600000000000 1715497 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": 1228626, "vin": [ { "gen": { "height": 1228616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b85d83eae9c531f7c85000f17fc15119a18eb5d36a23ac7794e464fda9699624" } } ], "extra": [ 1, 28, 189, 66, 50, 94, 21, 89, 20, 245, 239, 28, 126, 99, 171, 92, 75, 101, 75, 196, 23, 92, 45, 214, 254, 165, 231, 102, 1, 160, 125, 186, 251, 2, 17, 0, 0, 0, 13, 31, 10, 83, 235, 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