Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3832968afd15413ca5f1cb0052d9c751096d243dc5f157f030e7605f3e831b07

Tx prefix hash: 2d5c53faf54fe7ec2b552c8b8619481272b330f706e11725d36c2da2762e3332
Tx public key: ececd0e9d90fcf90072a63f64dac0b6bb6daa2ce83c451c19122e9927fed262a
Timestamp: 1717981676 Timestamp [UCT]: 2024-06-10 01:07:56 Age [y:d:h:m:s]: 00:294:10:53:49
Block: 1040827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210425 RingCT/type: yes/0
Extra: 01ececd0e9d90fcf90072a63f64dac0b6bb6daa2ce83c451c19122e9927fed262a021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f09bf20453dcd2c249ce072baf4a7b2fec5aefaca851f74853bc20d28d9fba6 0.600000000000 1509490 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": 1040837, "vin": [ { "gen": { "height": 1040827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f09bf20453dcd2c249ce072baf4a7b2fec5aefaca851f74853bc20d28d9fba6" } } ], "extra": [ 1, 236, 236, 208, 233, 217, 15, 207, 144, 7, 42, 99, 246, 77, 172, 11, 107, 182, 218, 162, 206, 131, 196, 81, 193, 145, 34, 233, 146, 127, 237, 38, 42, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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