Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e3c8acb4540039cff95de150edbeb073e2725f0d542f57a593e6244bd65c145

Tx prefix hash: 888072ee3c643daddfcf56cf1ca8b40ee80aab0983f56612c111e9eb38dc86a2
Tx public key: 486f1252fd6bc0aaefd674a1997d2ff0d0d10c68d9ea13202dc10b31cc83a383
Timestamp: 1705058006 Timestamp [UCT]: 2024-01-12 11:13:26 Age [y:d:h:m:s]: 01:044:20:56:40
Block: 933666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293134 RingCT/type: yes/0
Extra: 01486f1252fd6bc0aaefd674a1997d2ff0d0d10c68d9ea13202dc10b31cc83a3830211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9e30223f330f9f6b8b22f4c176f65347e8a623944daa07b201d3855b90b9f7a 0.600000000000 1391636 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": 933676, "vin": [ { "gen": { "height": 933666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9e30223f330f9f6b8b22f4c176f65347e8a623944daa07b201d3855b90b9f7a" } } ], "extra": [ 1, 72, 111, 18, 82, 253, 107, 192, 170, 239, 214, 116, 161, 153, 125, 47, 240, 208, 209, 12, 104, 217, 234, 19, 32, 45, 193, 11, 49, 204, 131, 163, 131, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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