Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a2972388bb8fb8a11c5f92ac244fe205f70b0f61ddc7930781e2fda370368f2

Tx prefix hash: ebd4075c31a3a99417984592e55a827a859c584297c6db2135932f4bfdea27bc
Tx public key: 60350f545d1469f1b693b7399d4dae13c2016cd21789cae2fb818ceecedbf975
Timestamp: 1681141810 Timestamp [UCT]: 2023-04-10 15:50:10 Age [y:d:h:m:s]: 02:021:20:20:29
Block: 735644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 537776 RingCT/type: yes/0
Extra: 0160350f545d1469f1b693b7399d4dae13c2016cd21789cae2fb818ceecedbf9750211000000025029cbac000000000000000000

1 output(s) for total of 2.241332414000 dcy

stealth address amount amount idx
00: 31e5d6fd7a7fa0feaf7c5aeea24244df2325a14d9d1c672ef9adb764ea92d4e1 2.241332414000 1181991 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": 735654, "vin": [ { "gen": { "height": 735644 } } ], "vout": [ { "amount": 2241332414, "target": { "key": "31e5d6fd7a7fa0feaf7c5aeea24244df2325a14d9d1c672ef9adb764ea92d4e1" } } ], "extra": [ 1, 96, 53, 15, 84, 93, 20, 105, 241, 182, 147, 183, 57, 157, 77, 174, 19, 194, 1, 108, 210, 23, 137, 202, 226, 251, 129, 140, 238, 206, 219, 249, 117, 2, 17, 0, 0, 0, 2, 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