Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 260c3a5bd00bb1c9696c37aea61347d272f00318dcc0695a80b2e1a048559bd5

Tx prefix hash: 0fa59ebb9378409651f72d00a0e52b82e060fd14bdba339a6b3e90118d24d2a9
Tx public key: d06a0ec9c0607176efc1292e5ac7cb751aff1f7c3e59961865c5f8e0ba2cf926
Timestamp: 1763239969 Timestamp [UCT]: 2025-11-15 20:52:49 Age [y:d:h:m:s]: 00:012:09:33:33
Block: 1412910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8877 RingCT/type: yes/0
Extra: 01d06a0ec9c0607176efc1292e5ac7cb751aff1f7c3e59961865c5f8e0ba2cf92602110000000243b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 465cf41167c8b1a75582600a1fc253fe796013fb09d0ea0a2ef87c304fb43ffd 0.600000000000 1901387 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": 1412920, "vin": [ { "gen": { "height": 1412910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "465cf41167c8b1a75582600a1fc253fe796013fb09d0ea0a2ef87c304fb43ffd" } } ], "extra": [ 1, 208, 106, 14, 201, 192, 96, 113, 118, 239, 193, 41, 46, 90, 199, 203, 117, 26, 255, 31, 124, 62, 89, 150, 24, 101, 197, 248, 224, 186, 44, 249, 38, 2, 17, 0, 0, 0, 2, 67, 181, 4, 113, 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