Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b753635432c264328dff29faa9327063f13da8c04a3dac6e0fd0064e551b43c

Tx prefix hash: 260b9a3006dbc4a1ec24a7e6b9e5e5d231a81f0998ce8f8302494415f8183e75
Tx public key: 8f755a142c7eedf34dc84ef379dfa68b993495d6a9bdb61e4bf60c485e8a4449
Timestamp: 1730113508 Timestamp [UCT]: 2024-10-28 11:05:08 Age [y:d:h:m:s]: 00:209:04:03:53
Block: 1141330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149369 RingCT/type: yes/0
Extra: 018f755a142c7eedf34dc84ef379dfa68b993495d6a9bdb61e4bf60c485e8a44490211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f91befbd8f2aa5a29c36ce690c35002051583f32062dcf5057f7584e62e920d0 0.600000000000 1625137 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": 1141340, "vin": [ { "gen": { "height": 1141330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f91befbd8f2aa5a29c36ce690c35002051583f32062dcf5057f7584e62e920d0" } } ], "extra": [ 1, 143, 117, 90, 20, 44, 126, 237, 243, 77, 200, 78, 243, 121, 223, 166, 139, 153, 52, 149, 214, 169, 189, 182, 30, 75, 246, 12, 72, 94, 138, 68, 73, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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