Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91091c99d7cdc331aecdb1cd177308c1e178c367c1914e7612e1fb0fa8300480

Tx prefix hash: 17b6bb9d4419044e1685e437569e726ad153e1273c2c09764a13e3d219ff005d
Tx public key: a3576586c2e44dbb0fb5cb919ce1eec8d592578c186587dfb673da9ae8eb4b95
Timestamp: 1737265205 Timestamp [UCT]: 2025-01-19 05:40:05 Age [y:d:h:m:s]: 00:054:10:22:09
Block: 1200504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38728 RingCT/type: yes/0
Extra: 01a3576586c2e44dbb0fb5cb919ce1eec8d592578c186587dfb673da9ae8eb4b950211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5135e44361b1528d1e277478105f31a3c536a20a21beb713eb9cbe4a3ee9cc6e 0.600000000000 1687149 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": 1200514, "vin": [ { "gen": { "height": 1200504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5135e44361b1528d1e277478105f31a3c536a20a21beb713eb9cbe4a3ee9cc6e" } } ], "extra": [ 1, 163, 87, 101, 134, 194, 228, 77, 187, 15, 181, 203, 145, 156, 225, 238, 200, 213, 146, 87, 140, 24, 101, 135, 223, 182, 115, 218, 154, 232, 235, 75, 149, 2, 17, 0, 0, 0, 5, 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