Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1067e5f8608d70de183c09ff12f483e474ac3a7021074667cc8c646c503c81d

Tx prefix hash: 6f9fb6db28fd7d39661f4b34ae6d0d943c45ce04d6343e33d0f57f80df702485
Tx public key: d1e24d7eb4f6eceaef254fb8512990826972c6feba86f910f925c62a48902dad
Timestamp: 1674728455 Timestamp [UCT]: 2023-01-26 10:20:55 Age [y:d:h:m:s]: 02:033:10:00:53
Block: 683105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545490 RingCT/type: yes/0
Extra: 01d1e24d7eb4f6eceaef254fb8512990826972c6feba86f910f925c62a48902dad0211000000015029cbac000000000000000000

1 output(s) for total of 3.346489777000 dcy

stealth address amount amount idx
00: 3f6f99dfbaeeea2edbca6ad8174c83651ee361a575885410c7acc4aa45c22d14 3.346489777000 1125266 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": 683115, "vin": [ { "gen": { "height": 683105 } } ], "vout": [ { "amount": 3346489777, "target": { "key": "3f6f99dfbaeeea2edbca6ad8174c83651ee361a575885410c7acc4aa45c22d14" } } ], "extra": [ 1, 209, 226, 77, 126, 180, 246, 236, 234, 239, 37, 79, 184, 81, 41, 144, 130, 105, 114, 198, 254, 186, 134, 249, 16, 249, 37, 198, 42, 72, 144, 45, 173, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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