Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bfec7d238a5f1673ce8e92d0264eabb809e9eb772e617f818212f8a5400bc64

Tx prefix hash: 31da3df562da35568ed834ac8c7908449e35132f0b13221c17748c7b9be1966a
Tx public key: b5f8f3973ce2b6b55cca8036ecfa51303287886b68d565eb7f90956ca684f9a9
Timestamp: 1578552745 Timestamp [UCT]: 2020-01-09 06:52:25 Age [y:d:h:m:s]: 05:064:23:09:29
Block: 41829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196382 RingCT/type: yes/0
Extra: 01b5f8f3973ce2b6b55cca8036ecfa51303287886b68d565eb7f90956ca684f9a902110000000b2264afe6000000000000000000

1 output(s) for total of 446.285704518000 dcy

stealth address amount amount idx
00: 1821556e596dfef6dc02e5aba59dae8e142b122033d96a2a02250d516f52f2fd 446.285704518000 74957 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": 41839, "vin": [ { "gen": { "height": 41829 } } ], "vout": [ { "amount": 446285704518, "target": { "key": "1821556e596dfef6dc02e5aba59dae8e142b122033d96a2a02250d516f52f2fd" } } ], "extra": [ 1, 181, 248, 243, 151, 60, 226, 182, 181, 92, 202, 128, 54, 236, 250, 81, 48, 50, 135, 136, 107, 104, 213, 101, 235, 127, 144, 149, 108, 166, 132, 249, 169, 2, 17, 0, 0, 0, 11, 34, 100, 175, 230, 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