Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33af2e3780d4a3aa1d42671cf2b8a4cd2d4d38eb3db607d087a3c336fca44617

Tx prefix hash: f68fa2664ac688c6719fba1ac206c41780dc6db9a1434d89a96b8de837c16d53
Tx public key: b549cf0b457cd8a26e47a9ae5612638748f5d17554c8db4e1e88017e760d78d4
Timestamp: 1736613711 Timestamp [UCT]: 2025-01-11 16:41:51 Age [y:d:h:m:s]: 00:158:12:38:29
Block: 1195145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112987 RingCT/type: yes/0
Extra: 01b549cf0b457cd8a26e47a9ae5612638748f5d17554c8db4e1e88017e760d78d40211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: def5f80e70371e771abbb8114b45d1d2370db48c03f61329a4fd01732f9faefc 0.600000000000 1681734 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": 1195155, "vin": [ { "gen": { "height": 1195145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "def5f80e70371e771abbb8114b45d1d2370db48c03f61329a4fd01732f9faefc" } } ], "extra": [ 1, 181, 73, 207, 11, 69, 124, 216, 162, 110, 71, 169, 174, 86, 18, 99, 135, 72, 245, 209, 117, 84, 200, 219, 78, 30, 136, 1, 126, 118, 13, 120, 212, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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