Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fd2f282115abcf0b081d093530a57f37af632815ff276ce756fbb3f0aafa6ac

Tx prefix hash: a9707831cd2abf014ac103c8e8ec4b5e92497a8ff5be56efb3e81dd2f758ff4e
Tx public key: 0ad4f90bcbb44ab2e320d56039b0e1700c77e81a49dac86cee7f78ddec14af92
Timestamp: 1724017480 Timestamp [UCT]: 2024-08-18 21:44:40 Age [y:d:h:m:s]: 00:226:05:31:15
Block: 1090869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161537 RingCT/type: yes/0
Extra: 010ad4f90bcbb44ab2e320d56039b0e1700c77e81a49dac86cee7f78ddec14af9202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0eb79ab5a7f2b765164b5f2c6592c6cb7de3b7e52f45f94b9b5db65be9ed409d 0.600000000000 1565494 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": 1090879, "vin": [ { "gen": { "height": 1090869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0eb79ab5a7f2b765164b5f2c6592c6cb7de3b7e52f45f94b9b5db65be9ed409d" } } ], "extra": [ 1, 10, 212, 249, 11, 203, 180, 74, 178, 227, 32, 213, 96, 57, 176, 225, 112, 12, 119, 232, 26, 73, 218, 200, 108, 238, 127, 120, 221, 236, 20, 175, 146, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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