Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81e5a93a6b3292ca026ee87a82911d059e81b461d2dd1ab4f657d347ca08a22f

Tx prefix hash: a7228169f2c9ce6fe718650fce0e7a6184a15bb644ee3a5cdd8e45c457bea9ff
Tx public key: bcffd6dd6972389f548f70ba4e52b36bb3bdf81c1012cabd2f29c630cc26e371
Timestamp: 1734841818 Timestamp [UCT]: 2024-12-22 04:30:18 Age [y:d:h:m:s]: 00:360:21:18:49
Block: 1180519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255452 RingCT/type: yes/0
Extra: 01bcffd6dd6972389f548f70ba4e52b36bb3bdf81c1012cabd2f29c630cc26e37102110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb069f759e33612a3ee8aec7b507e1c65e7e60f58681bb7cefe3d0dedef0a86b 0.600000000000 1666932 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": 1180529, "vin": [ { "gen": { "height": 1180519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb069f759e33612a3ee8aec7b507e1c65e7e60f58681bb7cefe3d0dedef0a86b" } } ], "extra": [ 1, 188, 255, 214, 221, 105, 114, 56, 159, 84, 143, 112, 186, 78, 82, 179, 107, 179, 189, 248, 28, 16, 18, 202, 189, 47, 41, 198, 48, 204, 38, 227, 113, 2, 17, 0, 0, 0, 10, 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