Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b480b9005420e00977a6b48b55b2b56631055efbc8eb78fa4ade5eb010c83f45

Tx prefix hash: 990b64c4e2d58f31500519e380abae56beebcc2c55a4fc519ef4c91484d81544
Tx public key: 5a0805e203c71d67e11d8082be65b663a25f2f3c5111e2a2ac252c0ecf82b068
Timestamp: 1711688086 Timestamp [UCT]: 2024-03-29 04:54:46 Age [y:d:h:m:s]: 00:287:13:55:20
Block: 988654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205845 RingCT/type: yes/0
Extra: 015a0805e203c71d67e11d8082be65b663a25f2f3c5111e2a2ac252c0ecf82b0680211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df0d0ce4a4a01dfdf2158989722c8a9df58385eebb901a9a905ddd99ccc616ad 0.600000000000 1448935 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": 988664, "vin": [ { "gen": { "height": 988654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df0d0ce4a4a01dfdf2158989722c8a9df58385eebb901a9a905ddd99ccc616ad" } } ], "extra": [ 1, 90, 8, 5, 226, 3, 199, 29, 103, 225, 29, 128, 130, 190, 101, 182, 99, 162, 95, 47, 60, 81, 17, 226, 162, 172, 37, 44, 14, 207, 130, 176, 104, 2, 17, 0, 0, 0, 2, 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