Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dab90e35658ce71f658a0607ca77e883f0991f52530343e0f2935d6534cc6c5

Tx prefix hash: 4438598c58bd2a304352590851b0a0385c1ae5157c4c5e706df0ae1ca1edef4c
Tx public key: c37a896b9ccafefc921de59beacd11f2d2b6025d771c345b4e75d339d9153f09
Timestamp: 1617065836 Timestamp [UCT]: 2021-03-30 00:57:16 Age [y:d:h:m:s]: 03:231:03:43:27
Block: 229358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 924647 RingCT/type: yes/0
Extra: 01c37a896b9ccafefc921de59beacd11f2d2b6025d771c345b4e75d339d9153f090211000000d0a9e81d35000000000000000000

1 output(s) for total of 106.671855506000 dcy

stealth address amount amount idx
00: b138171280e12b715e315271da9d55ee7c3df09161a1b642f5adb153457cbf6b 106.671855506000 475868 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": 229368, "vin": [ { "gen": { "height": 229358 } } ], "vout": [ { "amount": 106671855506, "target": { "key": "b138171280e12b715e315271da9d55ee7c3df09161a1b642f5adb153457cbf6b" } } ], "extra": [ 1, 195, 122, 137, 107, 156, 202, 254, 252, 146, 29, 229, 155, 234, 205, 17, 242, 210, 182, 2, 93, 119, 28, 52, 91, 78, 117, 211, 57, 217, 21, 63, 9, 2, 17, 0, 0, 0, 208, 169, 232, 29, 53, 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