Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 094c03caff3f83978b2abf26f7c2c2a3248b43efb2a634454d1eeb850651a526

Tx prefix hash: 98e8acf5cecaa564334ba73bd7f352fb23a9303cf6fb5bfb94d1257a51715104
Tx public key: 060a7312a6a652fc9018542067fb263f2b7ac2c16d09c12c92cd7e36e30c1bf4
Timestamp: 1731593827 Timestamp [UCT]: 2024-11-14 14:17:07 Age [y:d:h:m:s]: 00:140:11:37:45
Block: 1153578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100219 RingCT/type: yes/0
Extra: 01060a7312a6a652fc9018542067fb263f2b7ac2c16d09c12c92cd7e36e30c1bf4021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ece0e960ab67b8fcb7659f481931e14a785ad6deb0bef99131aac5872f6f0b05 0.600000000000 1639187 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": 1153588, "vin": [ { "gen": { "height": 1153578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ece0e960ab67b8fcb7659f481931e14a785ad6deb0bef99131aac5872f6f0b05" } } ], "extra": [ 1, 6, 10, 115, 18, 166, 166, 82, 252, 144, 24, 84, 32, 103, 251, 38, 63, 43, 122, 194, 193, 109, 9, 193, 44, 146, 205, 126, 54, 227, 12, 27, 244, 2, 17, 0, 0, 0, 4, 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