Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c423862dde74e17df75b59304252506c4cc5a3865ce8c98a9440b366266f81c5

Tx prefix hash: 977e1171214ee5b22d0cc3874ae1a92f36f6edcbbbca6a70efbd0826edc28c70
Tx public key: effdc474aac1e15376e13ef8b38d84660b8687b84f9ea982de4ed5f7d50015cd
Timestamp: 1737406958 Timestamp [UCT]: 2025-01-20 21:02:38 Age [y:d:h:m:s]: 00:148:21:24:48
Block: 1201678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106145 RingCT/type: yes/0
Extra: 01effdc474aac1e15376e13ef8b38d84660b8687b84f9ea982de4ed5f7d50015cd021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43b11c04d0220bbb833df6301c032e6fd75f5a976fa61c00a23a7b277e08bcec 0.600000000000 1688335 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": 1201688, "vin": [ { "gen": { "height": 1201678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43b11c04d0220bbb833df6301c032e6fd75f5a976fa61c00a23a7b277e08bcec" } } ], "extra": [ 1, 239, 253, 196, 116, 170, 193, 225, 83, 118, 225, 62, 248, 179, 141, 132, 102, 11, 134, 135, 184, 79, 158, 169, 130, 222, 78, 213, 247, 213, 0, 21, 205, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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