Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53c6b9cd166ebacb254edae92da1429a98d8288e034e51c6e937437b4822e380

Tx prefix hash: 47102ed3e98d7e9d597e395f726f7e5c779a8f185fe580626dc9354d40b0e7db
Tx public key: ad2f1f592bf237b66cf82acbe2da9d7ca5a24141eb79ac3c1e3220c06909bf54
Timestamp: 1725938082 Timestamp [UCT]: 2024-09-10 03:14:42 Age [y:d:h:m:s]: 00:188:02:49:22
Block: 1106785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134291 RingCT/type: yes/0
Extra: 01ad2f1f592bf237b66cf82acbe2da9d7ca5a24141eb79ac3c1e3220c06909bf54021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4d29f734369e1e3b281f6881325dce10337f92a0d51a27327b4da75ca51c129 0.600000000000 1584386 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": 1106795, "vin": [ { "gen": { "height": 1106785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4d29f734369e1e3b281f6881325dce10337f92a0d51a27327b4da75ca51c129" } } ], "extra": [ 1, 173, 47, 31, 89, 43, 242, 55, 182, 108, 248, 42, 203, 226, 218, 157, 124, 165, 162, 65, 65, 235, 121, 172, 60, 30, 50, 32, 192, 105, 9, 191, 84, 2, 17, 0, 0, 0, 3, 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