Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bbee76fed311b46a93ffe70ac8105e9eece1b93fc30940717a9acd8924c994a

Tx prefix hash: f17263b598ccbc07a24107eaee27bc3942dc3b1c1691a071ad023cab9803ffa2
Tx public key: 87430a823b16c8ad7aaa6893d2cb7dfb6b2eeb5a0deebec93bfcce2cdcf83207
Timestamp: 1730735154 Timestamp [UCT]: 2024-11-04 15:45:54 Age [y:d:h:m:s]: 00:156:02:53:57
Block: 1146470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111409 RingCT/type: yes/0
Extra: 0187430a823b16c8ad7aaa6893d2cb7dfb6b2eeb5a0deebec93bfcce2cdcf832070211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15876c0f8d0e8627a48f8dd15b429a04a66981ac15e6a8b9631a728ee98e9614 0.600000000000 1631115 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": 1146480, "vin": [ { "gen": { "height": 1146470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15876c0f8d0e8627a48f8dd15b429a04a66981ac15e6a8b9631a728ee98e9614" } } ], "extra": [ 1, 135, 67, 10, 130, 59, 22, 200, 173, 122, 170, 104, 147, 210, 203, 125, 251, 107, 46, 235, 90, 13, 238, 190, 201, 59, 252, 206, 44, 220, 248, 50, 7, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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