Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49d5ae7f1dd8fdc0a2bf21a4c9e3799c0ece14ab802811ab19abb76df479f784

Tx prefix hash: eeb21347309d1b1f7d87f8765dd0861ac38d16597d07571aadec7874cfb74ec9
Tx public key: e50d871ac9211a5114acdc077aea20f34020a140a816a1c72abaf709610fe317
Timestamp: 1731806584 Timestamp [UCT]: 2024-11-17 01:23:04 Age [y:d:h:m:s]: 00:210:11:44:04
Block: 1155331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150214 RingCT/type: yes/0
Extra: 01e50d871ac9211a5114acdc077aea20f34020a140a816a1c72abaf709610fe317021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e0c7b2f8d5b0274d8483c5a343d98ad259a564dec2df4a24780ed1edbc44dca 0.600000000000 1640946 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": 1155341, "vin": [ { "gen": { "height": 1155331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e0c7b2f8d5b0274d8483c5a343d98ad259a564dec2df4a24780ed1edbc44dca" } } ], "extra": [ 1, 229, 13, 135, 26, 201, 33, 26, 81, 20, 172, 220, 7, 122, 234, 32, 243, 64, 32, 161, 64, 168, 22, 161, 199, 42, 186, 247, 9, 97, 15, 227, 23, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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