Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7381bf12789beb6a3022cf2bd3c926cab28fce73377fc082ca76ce15f26f253

Tx prefix hash: 9f96debfe2961ed613c4b1e60eb453202327b2b36f0f54101074b8b3fe9b2ebd
Tx public key: db4f52e818fbb900268d45d3d717354e21f67a81d1a0c733eeed25e61c22c1dd
Timestamp: 1723838175 Timestamp [UCT]: 2024-08-16 19:56:15 Age [y:d:h:m:s]: 00:148:08:24:36
Block: 1089375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106118 RingCT/type: yes/0
Extra: 01db4f52e818fbb900268d45d3d717354e21f67a81d1a0c733eeed25e61c22c1dd021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79f4ebe5c77e3abbdda1610740b80b1ef8699befb01b89f2259b855ac60bacd3 0.600000000000 1563994 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": 1089385, "vin": [ { "gen": { "height": 1089375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79f4ebe5c77e3abbdda1610740b80b1ef8699befb01b89f2259b855ac60bacd3" } } ], "extra": [ 1, 219, 79, 82, 232, 24, 251, 185, 0, 38, 141, 69, 211, 215, 23, 53, 78, 33, 246, 122, 129, 209, 160, 199, 51, 238, 237, 37, 230, 28, 34, 193, 221, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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