Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9555c2f1713f256782f57a3ccae911c092affabe152d86b144605974da1e00af

Tx prefix hash: b8fc4e396abf40c73f4bc1895084246c9fb977e2a2e139f2fec94a05591312cb
Tx public key: 083fdc3e7b1a90fc268dce37d7b3e8456978190de0e96e1723a58969f1cf74e4
Timestamp: 1734398614 Timestamp [UCT]: 2024-12-17 01:23:34 Age [y:d:h:m:s]: 00:169:04:34:05
Block: 1176831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120747 RingCT/type: yes/0
Extra: 01083fdc3e7b1a90fc268dce37d7b3e8456978190de0e96e1723a58969f1cf74e40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 202f3c2ac6c20ea611a939ced855d1ef98cd484b2e618259d88b66a1a5fdb43b 0.600000000000 1663192 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": 1176841, "vin": [ { "gen": { "height": 1176831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "202f3c2ac6c20ea611a939ced855d1ef98cd484b2e618259d88b66a1a5fdb43b" } } ], "extra": [ 1, 8, 63, 220, 62, 123, 26, 144, 252, 38, 141, 206, 55, 215, 179, 232, 69, 105, 120, 25, 13, 224, 233, 110, 23, 35, 165, 137, 105, 241, 207, 116, 228, 2, 17, 0, 0, 0, 3, 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