Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d228febdbdb14f5c4411e70f164dc613255adc07ab94f4635ccb7c640dc6d9f8

Tx prefix hash: 6196dc22353d87fb00834930bec1a160d91ed6bee9034f8c1c0a1842a476994a
Tx public key: 45882e02fa18e04b4af49e0bd9d6ba8bb47cc8f72465091c870d473f96e21f64
Timestamp: 1675132947 Timestamp [UCT]: 2023-01-31 02:42:27 Age [y:d:h:m:s]: 02:066:19:45:11
Block: 686460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569379 RingCT/type: yes/0
Extra: 0145882e02fa18e04b4af49e0bd9d6ba8bb47cc8f72465091c870d473f96e21f640211000000035029cbac000000000000000000

1 output(s) for total of 3.261917630000 dcy

stealth address amount amount idx
00: fa3ae36bcde70ea7deb01eabac99ec63473b1654db1e126aa063618f49df972c 3.261917630000 1128953 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": 686470, "vin": [ { "gen": { "height": 686460 } } ], "vout": [ { "amount": 3261917630, "target": { "key": "fa3ae36bcde70ea7deb01eabac99ec63473b1654db1e126aa063618f49df972c" } } ], "extra": [ 1, 69, 136, 46, 2, 250, 24, 224, 75, 74, 244, 158, 11, 217, 214, 186, 139, 180, 124, 200, 247, 36, 101, 9, 28, 135, 13, 71, 63, 150, 226, 31, 100, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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