Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1db4e2f80b9a74d32bbf5a87f0fc27db3c4cdc76efa1c3e131ebb2b352d0ef3

Tx prefix hash: 6eb83e9818be5cd604beb61a3d6c7d32d026e5cfb0f84fd236ae87fd750363aa
Tx public key: 44328890a4658274b3b853d4479057991f800a0c62c43ecd47243ee8bb788ef0
Timestamp: 1706710579 Timestamp [UCT]: 2024-01-31 14:16:19 Age [y:d:h:m:s]: 01:142:06:42:13
Block: 947360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362634 RingCT/type: yes/0
Extra: 0144328890a4658274b3b853d4479057991f800a0c62c43ecd47243ee8bb788ef00211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f94f42c1fa6b06a43c3022c9df4f4b1d5b315605edb959b2f10095445b818dfb 0.600000000000 1405708 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": 947370, "vin": [ { "gen": { "height": 947360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f94f42c1fa6b06a43c3022c9df4f4b1d5b315605edb959b2f10095445b818dfb" } } ], "extra": [ 1, 68, 50, 136, 144, 164, 101, 130, 116, 179, 184, 83, 212, 71, 144, 87, 153, 31, 128, 10, 12, 98, 196, 62, 205, 71, 36, 62, 232, 187, 120, 142, 240, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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