Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70df017f8e6644409c830208b016c958353097669a196756f1f348a3d0b7b10e

Tx prefix hash: af5a726b9444b9f06de82b03295f1fe4c5e5482a0ad247ae8fec156052d99f96
Tx public key: 2210790c068b63196cce20ac06c5b2361da4ae75c18acd129b1239cbf2eb6ea3
Timestamp: 1737101368 Timestamp [UCT]: 2025-01-17 08:09:28 Age [y:d:h:m:s]: 00:058:16:34:16
Block: 1199185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41729 RingCT/type: yes/0
Extra: 012210790c068b63196cce20ac06c5b2361da4ae75c18acd129b1239cbf2eb6ea30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7ca1a73ae4fb82e01761e9dbc0dae2451586ddb5b5a21f595415dd209a31239 0.600000000000 1685814 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": 1199195, "vin": [ { "gen": { "height": 1199185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7ca1a73ae4fb82e01761e9dbc0dae2451586ddb5b5a21f595415dd209a31239" } } ], "extra": [ 1, 34, 16, 121, 12, 6, 139, 99, 25, 108, 206, 32, 172, 6, 197, 178, 54, 29, 164, 174, 117, 193, 138, 205, 18, 155, 18, 57, 203, 242, 235, 110, 163, 2, 17, 0, 0, 0, 3, 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