Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 948d90ca025552b73e0a1b75e83f5f781cc1c659f47430e14db9ce39f0cc43fb

Tx prefix hash: 7be84a0b7731a039526e28ca6046ae2b5eb5a2aa11fb353de8c1e9bd0736b498
Tx public key: 38e9f2492930eba5fff1aa9594aff59f8463669108f11a55784ca2ece99e3534
Timestamp: 1760497350 Timestamp [UCT]: 2025-10-15 03:02:30 Age [y:d:h:m:s]: 00:026:04:29:27
Block: 1390180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18756 RingCT/type: yes/0
Extra: 0138e9f2492930eba5fff1aa9594aff59f8463669108f11a55784ca2ece99e35340211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bb90f066085b8d821982a0b29d21f30cdfa0ad0f193ef3a9ddafd08eae5cdb7 0.600000000000 1878411 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": 1390190, "vin": [ { "gen": { "height": 1390180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bb90f066085b8d821982a0b29d21f30cdfa0ad0f193ef3a9ddafd08eae5cdb7" } } ], "extra": [ 1, 56, 233, 242, 73, 41, 48, 235, 165, 255, 241, 170, 149, 148, 175, 245, 159, 132, 99, 102, 145, 8, 241, 26, 85, 120, 76, 162, 236, 233, 158, 53, 52, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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