Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d23a34184fd38899f3d47564f29ad2abf9fef093e5d8cadfc472e4097a48c68

Tx prefix hash: d5c093ff58e3db48d6e008602a8564b171d1458c0d058e0d8363f5eea8d4ae80
Tx public key: 598988949ede53a81a7627a0a54867ec452fc239ce49cc9991cd9e3c1af22a47
Timestamp: 1721464946 Timestamp [UCT]: 2024-07-20 08:42:26 Age [y:d:h:m:s]: 00:191:10:30:56
Block: 1069698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136728 RingCT/type: yes/0
Extra: 01598988949ede53a81a7627a0a54867ec452fc239ce49cc9991cd9e3c1af22a47021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b286a82072e21f944ad29500fc67d7dd0a8bc3d024f654d8bb7d83d1cfe7b45a 0.600000000000 1541231 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": 1069708, "vin": [ { "gen": { "height": 1069698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b286a82072e21f944ad29500fc67d7dd0a8bc3d024f654d8bb7d83d1cfe7b45a" } } ], "extra": [ 1, 89, 137, 136, 148, 158, 222, 83, 168, 26, 118, 39, 160, 165, 72, 103, 236, 69, 47, 194, 57, 206, 73, 204, 153, 145, 205, 158, 60, 26, 242, 42, 71, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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