Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30eb743a6bc5bb9e3ea2d1f353f84ec75734659e80f9ed7b0f04b809288d3762

Tx prefix hash: 71789e996e4d16b937223332bf76d3df3bfa1006f95a598dbe2d449353d4d86a
Tx public key: 052584081b4aa1f9178e246e791e5531ed5980c5831120dd8a0349ff5e13aa5b
Timestamp: 1717532325 Timestamp [UCT]: 2024-06-04 20:18:45 Age [y:d:h:m:s]: 01:013:22:11:43
Block: 1037106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270721 RingCT/type: yes/0
Extra: 01052584081b4aa1f9178e246e791e5531ed5980c5831120dd8a0349ff5e13aa5b02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85bd59c5684d4976be6d30ba6ec9c9da1a5eb601abf496606f1aebaff2597289 0.600000000000 1505637 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": 1037116, "vin": [ { "gen": { "height": 1037106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85bd59c5684d4976be6d30ba6ec9c9da1a5eb601abf496606f1aebaff2597289" } } ], "extra": [ 1, 5, 37, 132, 8, 27, 74, 161, 249, 23, 142, 36, 110, 121, 30, 85, 49, 237, 89, 128, 197, 131, 17, 32, 221, 138, 3, 73, 255, 94, 19, 170, 91, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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