Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 619585bb5034a03fb97a1b22acb4667b35034f20b09df68d6775d3baf3f61210

Tx prefix hash: 0495d77ca1f4fb1835dcf513f6034d4c9a4fe5b4105842a6d9cafc8ff80d72a5
Tx public key: 78de8c1e90475d98f9015838870decf92791ad28d4f2f74425288d8eee6b4a33
Timestamp: 1735692649 Timestamp [UCT]: 2025-01-01 00:50:49 Age [y:d:h:m:s]: 00:136:01:19:45
Block: 1187518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97058 RingCT/type: yes/0
Extra: 0178de8c1e90475d98f9015838870decf92791ad28d4f2f74425288d8eee6b4a330211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 435e13484191704d4c179942dc20f412b241859d66a25c4f549dc11c8311c29c 0.600000000000 1674009 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": 1187528, "vin": [ { "gen": { "height": 1187518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "435e13484191704d4c179942dc20f412b241859d66a25c4f549dc11c8311c29c" } } ], "extra": [ 1, 120, 222, 140, 30, 144, 71, 93, 152, 249, 1, 88, 56, 135, 13, 236, 249, 39, 145, 173, 40, 212, 242, 247, 68, 37, 40, 141, 142, 238, 107, 74, 51, 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