Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 917843c310cd147ecbfc1cbeec89cae99fafee1f8531d458d11f25375d9e5abe

Tx prefix hash: 869b3f9b724e766a6abde8d702c2dfcb58396d8d30c6fb212980b7aa236223f0
Tx public key: 9b055bb6fbba6edbf710a843eeeaaab6f5a7eeb77f56e63ae31ff18b2441ed32
Timestamp: 1744098032 Timestamp [UCT]: 2025-04-08 07:40:32 Age [y:d:h:m:s]: 00:276:03:04:10
Block: 1256833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195152 RingCT/type: yes/0
Extra: 019b055bb6fbba6edbf710a843eeeaaab6f5a7eeb77f56e63ae31ff18b2441ed32021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fc600406291fe888236fc6aa097c3e34e9677e61bc7639e067d61dc28f26360 0.600000000000 1743950 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": 1256843, "vin": [ { "gen": { "height": 1256833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fc600406291fe888236fc6aa097c3e34e9677e61bc7639e067d61dc28f26360" } } ], "extra": [ 1, 155, 5, 91, 182, 251, 186, 110, 219, 247, 16, 168, 67, 238, 234, 170, 182, 245, 167, 238, 183, 127, 86, 230, 58, 227, 31, 241, 139, 36, 65, 237, 50, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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