Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5243c72d0fabe2574c7f43c1cfa85bc4b6c42d73d8be83ab5a223257cdf79498

Tx prefix hash: 58d893a276ba3b1a2766b1c58bf411df63f37be00f96cc167d2fb842fbb39d9c
Tx public key: 1ddda5c7a6bbf3fe0cc2dbd89f17e7164c1f74e5c39447af631ddbbf9bdb29ee
Timestamp: 1738284080 Timestamp [UCT]: 2025-01-31 00:41:20 Age [y:d:h:m:s]: 00:137:03:36:33
Block: 1208717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97985 RingCT/type: yes/0
Extra: 011ddda5c7a6bbf3fe0cc2dbd89f17e7164c1f74e5c39447af631ddbbf9bdb29ee021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42faa8426bb7155411747133ead7b8d3bf79b611094d7dc987f016866a5a0517 0.600000000000 1695450 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": 1208727, "vin": [ { "gen": { "height": 1208717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42faa8426bb7155411747133ead7b8d3bf79b611094d7dc987f016866a5a0517" } } ], "extra": [ 1, 29, 221, 165, 199, 166, 187, 243, 254, 12, 194, 219, 216, 159, 23, 231, 22, 76, 31, 116, 229, 195, 148, 71, 175, 99, 29, 219, 191, 155, 219, 41, 238, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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