Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f459b0215e8fbe88672eab9fd0755748b0c5242e42801b16d9825431cf5b627

Tx prefix hash: 6c9a09c4a3176e3530092f0f9013985f2427c75467ee497893d1200e73102924
Tx public key: 50acafbb40c1d2fa3066ea8b3cf4e45a517a9395afe4665b600b0b96aa276c0e
Timestamp: 1705528743 Timestamp [UCT]: 2024-01-17 21:59:03 Age [y:d:h:m:s]: 01:075:08:09:41
Block: 937562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314930 RingCT/type: yes/0
Extra: 0150acafbb40c1d2fa3066ea8b3cf4e45a517a9395afe4665b600b0b96aa276c0e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ad73559cd68ddba0f3dd0ecc87ebd21cc8e0edbdbfcb5884a9307cbd02a1234 0.600000000000 1395618 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": 937572, "vin": [ { "gen": { "height": 937562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ad73559cd68ddba0f3dd0ecc87ebd21cc8e0edbdbfcb5884a9307cbd02a1234" } } ], "extra": [ 1, 80, 172, 175, 187, 64, 193, 210, 250, 48, 102, 234, 139, 60, 244, 228, 90, 81, 122, 147, 149, 175, 228, 102, 91, 96, 11, 11, 150, 170, 39, 108, 14, 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