Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ff80d9db44be3ec549bfc0f61514fa7ec22cee6c8c0b14bed36f8845d6438d2

Tx prefix hash: 5752e56495ba5238ae3b4b5226e65af04eeb3e0a4711f1ca56b1f3d45e487849
Tx public key: 2f83c63a710f4e39cd1703d5188604b7e102298fcb64633840040e255e6b1dc2
Timestamp: 1717648713 Timestamp [UCT]: 2024-06-06 04:38:33 Age [y:d:h:m:s]: 01:154:09:06:29
Block: 1038064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368901 RingCT/type: yes/0
Extra: 012f83c63a710f4e39cd1703d5188604b7e102298fcb64633840040e255e6b1dc2021100000004d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: daec1d8a457488063ce13e6db61fb8a4b719533a07db42a6c7ecfc3c1819a7df 0.600000000000 1506623 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": 1038074, "vin": [ { "gen": { "height": 1038064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "daec1d8a457488063ce13e6db61fb8a4b719533a07db42a6c7ecfc3c1819a7df" } } ], "extra": [ 1, 47, 131, 198, 58, 113, 15, 78, 57, 205, 23, 3, 213, 24, 134, 4, 183, 225, 2, 41, 143, 203, 100, 99, 56, 64, 4, 14, 37, 94, 107, 29, 194, 2, 17, 0, 0, 0, 4, 215, 73, 245, 17, 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