Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eca6a5b509d5c2e7fd6156fbc7f784ed4ef1b6101c5b33ce874e077ec7d9c86

Tx prefix hash: 1acd64091a66f5bdfb4e54af03f338fc551aa803bed506cac81de5183596b411
Tx public key: 10b264eb09b31ff4d06e703c718a1e2eeda38f078cb1137013627b5fcc14cbf4
Timestamp: 1702874550 Timestamp [UCT]: 2023-12-18 04:42:30 Age [y:d:h:m:s]: 01:140:23:06:52
Block: 915574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361898 RingCT/type: yes/0
Extra: 0110b264eb09b31ff4d06e703c718a1e2eeda38f078cb1137013627b5fcc14cbf4021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b69eda0bffcdb823db597498ba61a315856297e410a13ed11c822b0f039262a 0.600000000000 1372970 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": 915584, "vin": [ { "gen": { "height": 915574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b69eda0bffcdb823db597498ba61a315856297e410a13ed11c822b0f039262a" } } ], "extra": [ 1, 16, 178, 100, 235, 9, 179, 31, 244, 208, 110, 112, 60, 113, 138, 30, 46, 237, 163, 143, 7, 140, 177, 19, 112, 19, 98, 123, 95, 204, 20, 203, 244, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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