Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67e096f1cc451742bbeb063c4275d635ad4e915bd9d0e456e9ad7197c90f6eef

Tx prefix hash: f8e83c65465965903076cb1cc1b2436fd8551827e4eaa0077d314e4ed1a3fab5
Tx public key: 5f3015dedd7bf9776a7c0a0d7334df316e3b44cec1c5fff9eb9dc9875d1915e0
Timestamp: 1706782214 Timestamp [UCT]: 2024-02-01 10:10:14 Age [y:d:h:m:s]: 01:134:20:27:37
Block: 947954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357410 RingCT/type: yes/0
Extra: 015f3015dedd7bf9776a7c0a0d7334df316e3b44cec1c5fff9eb9dc9875d1915e002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78918ed33bd32a95543fa41c8b623ec791a0f439733f8d2096fa88bb47ce7fff 0.600000000000 1406316 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": 947964, "vin": [ { "gen": { "height": 947954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78918ed33bd32a95543fa41c8b623ec791a0f439733f8d2096fa88bb47ce7fff" } } ], "extra": [ 1, 95, 48, 21, 222, 221, 123, 249, 119, 106, 124, 10, 13, 115, 52, 223, 49, 110, 59, 68, 206, 193, 197, 255, 249, 235, 157, 201, 135, 93, 25, 21, 224, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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