Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ead2ec6955d60818574ec931750e3a9ad829c227ba232b33b93d07d91a9c7e59

Tx prefix hash: bed2cbfbcdaf0587a78b2274c11aab5df9b9d107cc0f57aff68ac28e20922b57
Tx public key: 1b41db452e22b2c652c2d624b9d13b4940ca31d633b8baef02cf8539fe8383f5
Timestamp: 1736655076 Timestamp [UCT]: 2025-01-12 04:11:16 Age [y:d:h:m:s]: 00:161:17:14:22
Block: 1195486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115212 RingCT/type: yes/0
Extra: 011b41db452e22b2c652c2d624b9d13b4940ca31d633b8baef02cf8539fe8383f50211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae2f9b645eb2c5c0621014fc58542ee4fcb1f4a8fc1b2b0d26fb4e9630a6d8ef 0.600000000000 1682077 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": 1195496, "vin": [ { "gen": { "height": 1195486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae2f9b645eb2c5c0621014fc58542ee4fcb1f4a8fc1b2b0d26fb4e9630a6d8ef" } } ], "extra": [ 1, 27, 65, 219, 69, 46, 34, 178, 198, 82, 194, 214, 36, 185, 209, 59, 73, 64, 202, 49, 214, 51, 184, 186, 239, 2, 207, 133, 57, 254, 131, 131, 245, 2, 17, 0, 0, 0, 6, 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