Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b68df3dbdfae178948d62067b3ed9e84d4b158c639a876797e3603d44cd32e01

Tx prefix hash: 5d64fe88a07e4adcfa758c5fdc6fe8be7f962be1f2fd9bb7b527631828f2d260
Tx public key: 10e9bc9d2287bb7b98c92649f875e243b99ca935bc35cc24bb7bbd1823afb890
Timestamp: 1764944932 Timestamp [UCT]: 2025-12-05 14:28:52 Age [y:d:h:m:s]: 00:017:23:28:45
Block: 1427027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12871 RingCT/type: yes/0
Extra: 0110e9bc9d2287bb7b98c92649f875e243b99ca935bc35cc24bb7bbd1823afb890021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 559f43328215561d6cce1082f51ba8d286ec8b7dffeb580f4c2020596285b1b2 0.600000000000 1915726 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": 1427037, "vin": [ { "gen": { "height": 1427027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "559f43328215561d6cce1082f51ba8d286ec8b7dffeb580f4c2020596285b1b2" } } ], "extra": [ 1, 16, 233, 188, 157, 34, 135, 187, 123, 152, 201, 38, 73, 248, 117, 226, 67, 185, 156, 169, 53, 188, 53, 204, 36, 187, 123, 189, 24, 35, 175, 184, 144, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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