Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0f844daa36104c2f3617fea84f3f88fb758a152bc4e4082a94d67e40dd09a6

Tx prefix hash: 183ec1caae159e00094eec4b3f20a9e19ab5be512c90a6a763ebdfbe118e3b13
Tx public key: 657d8c555cdc6568787904f28e680dd7287ec7b982a781a6b2261f7e75bd51aa
Timestamp: 1706827497 Timestamp [UCT]: 2024-02-01 22:44:57 Age [y:d:h:m:s]: 01:027:22:53:08
Block: 948341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281012 RingCT/type: yes/0
Extra: 01657d8c555cdc6568787904f28e680dd7287ec7b982a781a6b2261f7e75bd51aa02110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85fb3a7e9a9b86484e30ab6eb03e2a14fae221824404ba1b9b0e997ca3eaf701 0.600000000000 1406727 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": 948351, "vin": [ { "gen": { "height": 948341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85fb3a7e9a9b86484e30ab6eb03e2a14fae221824404ba1b9b0e997ca3eaf701" } } ], "extra": [ 1, 101, 125, 140, 85, 92, 220, 101, 104, 120, 121, 4, 242, 142, 104, 13, 215, 40, 126, 199, 185, 130, 167, 129, 166, 178, 38, 31, 126, 117, 189, 81, 170, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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