Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16d90e6aefdccd34c0f5906b3245a37eabc89cddcfe5ec5fcda30349bb2e3c4d

Tx prefix hash: 746c7999e3362a23cfef743cfa7df7f5790fd311dbbe1ae050f14545f3658aea
Tx public key: 083c25afec5e23b3b91805fd3908dc6be416ff09a3a28983f3506792b288067a
Timestamp: 1681638104 Timestamp [UCT]: 2023-04-16 09:41:44 Age [y:d:h:m:s]: 01:364:01:46:14
Block: 739762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521492 RingCT/type: yes/0
Extra: 01083c25afec5e23b3b91805fd3908dc6be416ff09a3a28983f3506792b288067a0211000000015029cbac000000000000000000

1 output(s) for total of 2.172009009000 dcy

stealth address amount amount idx
00: ad9b3a22b1fc32064c705595f74d48d8ec2605f95ef9051f85617243789c8e1e 2.172009009000 1186635 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": 739772, "vin": [ { "gen": { "height": 739762 } } ], "vout": [ { "amount": 2172009009, "target": { "key": "ad9b3a22b1fc32064c705595f74d48d8ec2605f95ef9051f85617243789c8e1e" } } ], "extra": [ 1, 8, 60, 37, 175, 236, 94, 35, 179, 185, 24, 5, 253, 57, 8, 220, 107, 228, 22, 255, 9, 163, 162, 137, 131, 243, 80, 103, 146, 178, 136, 6, 122, 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