Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3b08978d8a59469e3afcf1d7f76b46458e936c2835f10f8db6959397533a413

Tx prefix hash: 562f09100790bf4e5357ad71984648431b4522a4aab4b8e96c1153109e8871f3
Tx public key: 4ac1b32ec70df90aeaa1a6a29a59c344a4ddd1d27cceb31e174b1847787c8b87
Timestamp: 1687147977 Timestamp [UCT]: 2023-06-19 04:12:57 Age [y:d:h:m:s]: 01:327:16:43:41
Block: 785440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495404 RingCT/type: yes/0
Extra: 014ac1b32ec70df90aeaa1a6a29a59c344a4ddd1d27cceb31e174b1847787c8b87021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.532891371000 dcy

stealth address amount amount idx
00: 64218e3d44c9681c37d522ec799124613201485a4fe77acc245e49879734defa 1.532891371000 1235397 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": 785450, "vin": [ { "gen": { "height": 785440 } } ], "vout": [ { "amount": 1532891371, "target": { "key": "64218e3d44c9681c37d522ec799124613201485a4fe77acc245e49879734defa" } } ], "extra": [ 1, 74, 193, 179, 46, 199, 13, 249, 10, 234, 161, 166, 162, 154, 89, 195, 68, 164, 221, 209, 210, 124, 206, 179, 30, 23, 75, 24, 71, 120, 124, 139, 135, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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