Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4a05baca3dd49949a9d8213d230bd92b96875ab8b164b4e1a5516dc8ba9de8b

Tx prefix hash: 6be2a2036c9690177474fedf5f54c86613cd88b11ba6cc1af734fb2ff681d091
Tx public key: bb9acb929ebba8e8ea155aa154a02c69f3d20e7b1535ce40e5792c137876cc72
Timestamp: 1701207014 Timestamp [UCT]: 2023-11-28 21:30:14 Age [y:d:h:m:s]: 01:342:23:37:57
Block: 901760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503987 RingCT/type: yes/0
Extra: 01bb9acb929ebba8e8ea155aa154a02c69f3d20e7b1535ce40e5792c137876cc72021100000003e08532b6000000000000000000

1 output(s) for total of 0.631095033000 dcy

stealth address amount amount idx
00: 05df81669b69cc6b6694e0331f1e6f4b1711132ebcda9289068c1f3138360e47 0.631095033000 1358349 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": 901770, "vin": [ { "gen": { "height": 901760 } } ], "vout": [ { "amount": 631095033, "target": { "key": "05df81669b69cc6b6694e0331f1e6f4b1711132ebcda9289068c1f3138360e47" } } ], "extra": [ 1, 187, 154, 203, 146, 158, 187, 168, 232, 234, 21, 90, 161, 84, 160, 44, 105, 243, 210, 14, 123, 21, 53, 206, 64, 229, 121, 44, 19, 120, 118, 204, 114, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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