Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc2ab365bf32e30985d2ae64fddd04166888bd10157b9df9298d34f6df84cb63

Tx prefix hash: 06625501118304a9f11e5345f41aa7462762bc86edbe64d2e0ff0266be95fdc6
Tx public key: c9d2ec8bd9f4850806971f1b303913d664bbac0fd6b0a100f1c34b444647df1f
Timestamp: 1664416522 Timestamp [UCT]: 2022-09-29 01:55:22 Age [y:d:h:m:s]: 02:202:12:47:16
Block: 597878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 666332 RingCT/type: yes/0
Extra: 01c9d2ec8bd9f4850806971f1b303913d664bbac0fd6b0a100f1c34b444647df1f021100000006faf35c9c000000000000000000

1 output(s) for total of 6.411830868000 dcy

stealth address amount amount idx
00: b74c35ce97e4e5f1be069e7f315c39e8506ccfda7acf5e2ea091b3dc9d066842 6.411830868000 1033535 of 0

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": 597888, "vin": [ { "gen": { "height": 597878 } } ], "vout": [ { "amount": 6411830868, "target": { "key": "b74c35ce97e4e5f1be069e7f315c39e8506ccfda7acf5e2ea091b3dc9d066842" } } ], "extra": [ 1, 201, 210, 236, 139, 217, 244, 133, 8, 6, 151, 31, 27, 48, 57, 19, 214, 100, 187, 172, 15, 214, 176, 161, 0, 241, 195, 75, 68, 70, 71, 223, 31, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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