Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46c98fa6753c29e1c3fb2b98ebfff8a2a640d11e99fd2d5d43613f3c351006bb

Tx prefix hash: 1ab44b8eaa9063f7f4ea279f3ad740735051655ce7a72a1745df00c10ae8e31e
Tx public key: 49547a30c4e93a35fc0f1dcdda539780984516a610487b64a98f1c51f30aca31
Timestamp: 1717168047 Timestamp [UCT]: 2024-05-31 15:07:27 Age [y:d:h:m:s]: 01:130:16:02:30
Block: 1034088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351911 RingCT/type: yes/0
Extra: 0149547a30c4e93a35fc0f1dcdda539780984516a610487b64a98f1c51f30aca310211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 137f531123df8b6e9fde7ab63f218f5f53f5e68ee95c3915905361ae7fe1768c 0.600000000000 1502561 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": 1034098, "vin": [ { "gen": { "height": 1034088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "137f531123df8b6e9fde7ab63f218f5f53f5e68ee95c3915905361ae7fe1768c" } } ], "extra": [ 1, 73, 84, 122, 48, 196, 233, 58, 53, 252, 15, 29, 205, 218, 83, 151, 128, 152, 69, 22, 166, 16, 72, 123, 100, 169, 143, 28, 81, 243, 10, 202, 49, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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