Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fac7c23bba36a00736c5325901aeb515106799529b39791a59ae075a0a4d1b54

Tx prefix hash: 14dec1a97cec5fcb338d7742afd7ddcd2c34882628e6030830d2403abddaf858
Tx public key: fb6ef1e8cad2f12d119a60a863baa775b7ed5d8b21ba19a2b31e59c6132a5d98
Timestamp: 1745855913 Timestamp [UCT]: 2025-04-28 15:58:33 Age [y:d:h:m:s]: 00:206:22:10:21
Block: 1271407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145588 RingCT/type: yes/0
Extra: 01fb6ef1e8cad2f12d119a60a863baa775b7ed5d8b21ba19a2b31e59c6132a5d9802110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 390f688da313ea7ebcc5e5d7ec5c38548c6f58254b6dfdffaf44ef9fdc4175aa 0.600000000000 1758668 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": 1271417, "vin": [ { "gen": { "height": 1271407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "390f688da313ea7ebcc5e5d7ec5c38548c6f58254b6dfdffaf44ef9fdc4175aa" } } ], "extra": [ 1, 251, 110, 241, 232, 202, 210, 241, 45, 17, 154, 96, 168, 99, 186, 167, 117, 183, 237, 93, 139, 33, 186, 25, 162, 179, 30, 89, 198, 19, 42, 93, 152, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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