Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16725c71f183103a2d4bfad3750f052beaee6971c94adf7185e1e80265f59b5c

Tx prefix hash: eac083e0350f4c2d7ea9733fe4f190663b0ccbe0d1a48973a0b7e39d6d0fc300
Tx public key: af86e8ef13dcfa1ad960c3cf7abc30759c5b4caf4a113ec17ddd824a9e06c13f
Timestamp: 1681636733 Timestamp [UCT]: 2023-04-16 09:18:53 Age [y:d:h:m:s]: 01:271:12:36:39
Block: 739745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455557 RingCT/type: yes/0
Extra: 01af86e8ef13dcfa1ad960c3cf7abc30759c5b4caf4a113ec17ddd824a9e06c13f021100000001faf35c9c000000000000000000

1 output(s) for total of 2.172290738000 dcy

stealth address amount amount idx
00: b303e933eedefcf3b3dc02c66a04a1d960eac08d2226123648d64c5f27dcff95 2.172290738000 1186614 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": 739755, "vin": [ { "gen": { "height": 739745 } } ], "vout": [ { "amount": 2172290738, "target": { "key": "b303e933eedefcf3b3dc02c66a04a1d960eac08d2226123648d64c5f27dcff95" } } ], "extra": [ 1, 175, 134, 232, 239, 19, 220, 250, 26, 217, 96, 195, 207, 122, 188, 48, 117, 156, 91, 76, 175, 74, 17, 62, 193, 125, 221, 130, 74, 158, 6, 193, 63, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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