Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bda7ba798d1ef8043d092cf9feb6b4a1e8174ad824a95ad46344683e540467f

Tx prefix hash: 8a161b05c806bf98c2ae626556377b50d6bd76dc0e51fa5f04e746ab4e1ef3ba
Tx public key: 7f60097ac59c604b4f12a369b01978daa53b50807b65333f4a1fc708e8204a17
Timestamp: 1732699981 Timestamp [UCT]: 2024-11-27 09:33:01 Age [y:d:h:m:s]: 00:124:04:10:34
Block: 1162751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88546 RingCT/type: yes/0
Extra: 017f60097ac59c604b4f12a369b01978daa53b50807b65333f4a1fc708e8204a17021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc0f0e1be2fcf0b653916b3416ca1a69bdcc97d768d186e18eac0b602b7d2d6f 0.600000000000 1648408 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": 1162761, "vin": [ { "gen": { "height": 1162751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc0f0e1be2fcf0b653916b3416ca1a69bdcc97d768d186e18eac0b602b7d2d6f" } } ], "extra": [ 1, 127, 96, 9, 122, 197, 156, 96, 75, 79, 18, 163, 105, 176, 25, 120, 218, 165, 59, 80, 128, 123, 101, 51, 63, 74, 31, 199, 8, 232, 32, 74, 23, 2, 17, 0, 0, 0, 2, 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