Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 216a568147b548830f39316b2a0dca8738a336f17d208c8d631ca0f705c91059

Tx prefix hash: 2af1d034952be0b5d01a14b2d6baf3484b61bd16bccd05a2710ba66f37de3154
Tx public key: 65ccb1b6a55c44e56fe0937beb9877528833d833696d384a23b6cc2ae9021bb5
Timestamp: 1712959701 Timestamp [UCT]: 2024-04-12 22:08:21 Age [y:d:h:m:s]: 01:222:00:19:38
Block: 999167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417363 RingCT/type: yes/0
Extra: 0165ccb1b6a55c44e56fe0937beb9877528833d833696d384a23b6cc2ae9021bb502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ceb8e3f5eb8e66d4dd2de6a173d6bb55f082e2f3c9447946a9f1d963a3352a6b 0.600000000000 1459645 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": 999177, "vin": [ { "gen": { "height": 999167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ceb8e3f5eb8e66d4dd2de6a173d6bb55f082e2f3c9447946a9f1d963a3352a6b" } } ], "extra": [ 1, 101, 204, 177, 182, 165, 92, 68, 229, 111, 224, 147, 123, 235, 152, 119, 82, 136, 51, 216, 51, 105, 109, 56, 74, 35, 182, 204, 42, 233, 2, 27, 181, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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