Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d71d58a3daffe9398a90233a679bb0c2ceb879e11019a5642c624ebd8d8410ce

Tx prefix hash: 4d6c15003aaf4355e4f938ffa21465e90b8840d23b68b549ed67fffb6a3bc2a9
Tx public key: 96705e88b61274c9269f0fe9ad4fc48f98f4a39b289b3db0f7fcb495ad2cb3ce
Timestamp: 1706833784 Timestamp [UCT]: 2024-02-02 00:29:44 Age [y:d:h:m:s]: 01:133:18:12:14
Block: 948391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356627 RingCT/type: yes/0
Extra: 0196705e88b61274c9269f0fe9ad4fc48f98f4a39b289b3db0f7fcb495ad2cb3ce02110000000310a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e776b66c3b6cc9e572f5bcc9439f5c65df4ab47c03ee9816a74e59578f95e8bb 0.600000000000 1406789 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": 948401, "vin": [ { "gen": { "height": 948391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e776b66c3b6cc9e572f5bcc9439f5c65df4ab47c03ee9816a74e59578f95e8bb" } } ], "extra": [ 1, 150, 112, 94, 136, 182, 18, 116, 201, 38, 159, 15, 233, 173, 79, 196, 143, 152, 244, 163, 155, 40, 155, 61, 176, 247, 252, 180, 149, 173, 44, 179, 206, 2, 17, 0, 0, 0, 3, 16, 161, 116, 143, 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