Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 546934bd648ee77d8041a616675e16b1765475c5183e9c2695fc5934eda92bde

Tx prefix hash: 8ad184784f7c2a0667c3ae6db82d94798fbcae8e09df55c014a3260822e0c74f
Tx public key: e9d4449f05a45dd0629c0ac9c9d073f458eb3bcc78beefed719255d662288bb5
Timestamp: 1577890843 Timestamp [UCT]: 2020-01-01 15:00:43 Age [y:d:h:m:s]: 05:302:03:46:05
Block: 36393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1363576 RingCT/type: yes/0
Extra: 01e9d4449f05a45dd0629c0ac9c9d073f458eb3bcc78beefed719255d662288bb502110000002f4ac5aa02000000000000000000

1 output(s) for total of 464.960154004000 dcy

stealth address amount amount idx
00: de3b753310ac137d3ee21a1401c01201d783f1b80c7d8f20f67b6089708c1a88 464.960154004000 61643 of 0

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": 36403, "vin": [ { "gen": { "height": 36393 } } ], "vout": [ { "amount": 464960154004, "target": { "key": "de3b753310ac137d3ee21a1401c01201d783f1b80c7d8f20f67b6089708c1a88" } } ], "extra": [ 1, 233, 212, 68, 159, 5, 164, 93, 208, 98, 156, 10, 201, 201, 208, 115, 244, 88, 235, 59, 204, 120, 190, 239, 237, 113, 146, 85, 214, 98, 40, 139, 181, 2, 17, 0, 0, 0, 47, 74, 197, 170, 2, 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