Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b6536adb9d513c9ff8e09fa9bd977dbb17289b1f805e02f6cc93034f6e79263

Tx prefix hash: d3834eb00a17e8eb592107414c077bb56e5cb60d0ad7c6304badb6e3ff7c3bd7
Tx public key: 231d43f375224f33357d03f87810b137cbf7d43b6092a65097e592de3e91f78d
Timestamp: 1660937743 Timestamp [UCT]: 2022-08-19 19:35:43 Age [y:d:h:m:s]: 03:073:22:02:49
Block: 569448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 832636 RingCT/type: yes/0
Extra: 01231d43f375224f33357d03f87810b137cbf7d43b6092a65097e592de3e91f78d02110000001333af99f4000000000000000000

1 output(s) for total of 7.964939671000 dcy

stealth address amount amount idx
00: 80a9ea3550069c545d7c7e69cc433f77c3cf0f7b2fc3423cc60adf227e7c4606 7.964939671000 1002597 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": 569458, "vin": [ { "gen": { "height": 569448 } } ], "vout": [ { "amount": 7964939671, "target": { "key": "80a9ea3550069c545d7c7e69cc433f77c3cf0f7b2fc3423cc60adf227e7c4606" } } ], "extra": [ 1, 35, 29, 67, 243, 117, 34, 79, 51, 53, 125, 3, 248, 120, 16, 177, 55, 203, 247, 212, 59, 96, 146, 166, 80, 151, 229, 146, 222, 62, 145, 247, 141, 2, 17, 0, 0, 0, 19, 51, 175, 153, 244, 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