Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5c4be74d58725ca5e6b33220ea1e2d9a74672ccfd6f4d4fedef50d5ac045f74

Tx prefix hash: 6b9aee739db0992db439bc04f9dc341e1957d3e72a832f78ccb0d3b2594d8388
Tx public key: e3fc3795dfc717d998684d4ca48f3ea88244465d3d2d4065608f066ad76cc48f
Timestamp: 1764514313 Timestamp [UCT]: 2025-11-30 14:51:53 Age [y:d:h:m:s]: 00:031:09:38:56
Block: 1423470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22484 RingCT/type: yes/0
Extra: 01e3fc3795dfc717d998684d4ca48f3ea88244465d3d2d4065608f066ad76cc48f021100000007defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc4c1940b356c12f620dca6811790d3841b4602a6b5859382659d860e46e8ec2 0.600000000000 1912083 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": 1423480, "vin": [ { "gen": { "height": 1423470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc4c1940b356c12f620dca6811790d3841b4602a6b5859382659d860e46e8ec2" } } ], "extra": [ 1, 227, 252, 55, 149, 223, 199, 23, 217, 152, 104, 77, 76, 164, 143, 62, 168, 130, 68, 70, 93, 61, 45, 64, 101, 96, 143, 6, 106, 215, 108, 196, 143, 2, 17, 0, 0, 0, 7, 222, 251, 143, 24, 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