Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18bbfec9dc304a0d597bf1eb574231b01cb51643e998a5c06b9b0e6358ae150a

Tx prefix hash: b7935cf8b2621e9511af8460ee8e3cd854071a79ff0bbc4edeb81cb86eac2cde
Tx public key: 1d82fb335c408ee1a67c7bd29b13a2cdefd64edec8da4e12bfc45402ea4090ec
Timestamp: 1705021034 Timestamp [UCT]: 2024-01-12 00:57:14 Age [y:d:h:m:s]: 01:121:11:23:38
Block: 933360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347941 RingCT/type: yes/0
Extra: 011d82fb335c408ee1a67c7bd29b13a2cdefd64edec8da4e12bfc45402ea4090ec0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6611ebea6cb30fdc565af2f1a80141bcbc0a930744c1078fe3f924be8863870 0.600000000000 1391322 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": 933370, "vin": [ { "gen": { "height": 933360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6611ebea6cb30fdc565af2f1a80141bcbc0a930744c1078fe3f924be8863870" } } ], "extra": [ 1, 29, 130, 251, 51, 92, 64, 142, 225, 166, 124, 123, 210, 155, 19, 162, 205, 239, 214, 78, 222, 200, 218, 78, 18, 191, 196, 84, 2, 234, 64, 144, 236, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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