Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2e010481a0b1de94f07530fe67b874943afbb53f45d66845c53900beac9bdd8

Tx prefix hash: ddb6bd567dafd86ef684fedc7842de307b33b2dc5b353ab96095ef22c735e4dd
Tx public key: acb9018ce887696fc0d2fdc956b1333f9a75eb4f9a723b9448bf9d1a6fa3c993
Timestamp: 1715764609 Timestamp [UCT]: 2024-05-15 09:16:49 Age [y:d:h:m:s]: 00:323:05:51:59
Block: 1022442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231044 RingCT/type: yes/0
Extra: 01acb9018ce887696fc0d2fdc956b1333f9a75eb4f9a723b9448bf9d1a6fa3c99302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdc1b527834690c065ecca1baf8875a22de09920c65a86e31fdf3ccb79511ae9 0.600000000000 1487049 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": 1022452, "vin": [ { "gen": { "height": 1022442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdc1b527834690c065ecca1baf8875a22de09920c65a86e31fdf3ccb79511ae9" } } ], "extra": [ 1, 172, 185, 1, 140, 232, 135, 105, 111, 192, 210, 253, 201, 86, 177, 51, 63, 154, 117, 235, 79, 154, 114, 59, 148, 72, 191, 157, 26, 111, 163, 201, 147, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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