Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 637b3e0c89cf98d77f1e4a7e8fc2d2e82fa0f40b21e106a0fb91919a6c0a67c3

Tx prefix hash: 7ddcf15c1f4d63e882452057c45e79c5db11bee8f3ac59fdd4c0e3bdd0dadc9d
Tx public key: ea55d785ee98bb052eabfe9a0d6f63e92ad35761e37a05a7b3a13bc887f62167
Timestamp: 1646270139 Timestamp [UCT]: 2022-03-03 01:15:39 Age [y:d:h:m:s]: 02:347:13:52:57
Block: 450138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 767602 RingCT/type: yes/0
Extra: 01ea55d785ee98bb052eabfe9a0d6f63e92ad35761e37a05a7b3a13bc887f62167021100000004cb8520c2000000000000000000

1 output(s) for total of 19.792753838000 dcy

stealth address amount amount idx
00: bcbd31f273ea473bb877fbef7b58622df43c5293b41c6affc7af3d72ad7e1e4f 19.792753838000 864939 of 0

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": 450148, "vin": [ { "gen": { "height": 450138 } } ], "vout": [ { "amount": 19792753838, "target": { "key": "bcbd31f273ea473bb877fbef7b58622df43c5293b41c6affc7af3d72ad7e1e4f" } } ], "extra": [ 1, 234, 85, 215, 133, 238, 152, 187, 5, 46, 171, 254, 154, 13, 111, 99, 233, 42, 211, 87, 97, 227, 122, 5, 167, 179, 161, 59, 200, 135, 246, 33, 103, 2, 17, 0, 0, 0, 4, 203, 133, 32, 194, 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