Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97a6ded1752223215d09f980a1730e9b3d489d875bdc4ea4c5e179fdfa389b93

Tx prefix hash: 2acddf169d724f1b5b86e71d01a707c9a38f3479c66978d13335abf8be648963
Tx public key: a1edf9b56fbdb38465c5eab471023725a076ccce9950f37738761d182975af4c
Timestamp: 1578879088 Timestamp [UCT]: 2020-01-13 01:31:28 Age [y:d:h:m:s]: 05:022:02:08:38
Block: 44284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165947 RingCT/type: yes/0
Extra: 01a1edf9b56fbdb38465c5eab471023725a076ccce9950f37738761d182975af4c02110000000d4943cd9f000000000000000000

1 output(s) for total of 437.793759034000 dcy

stealth address amount amount idx
00: 8e03349305a43e38c5a557275c56d3abd1ede6f904945a58bc285ef3e994dfd8 437.793759034000 80553 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": 44294, "vin": [ { "gen": { "height": 44284 } } ], "vout": [ { "amount": 437793759034, "target": { "key": "8e03349305a43e38c5a557275c56d3abd1ede6f904945a58bc285ef3e994dfd8" } } ], "extra": [ 1, 161, 237, 249, 181, 111, 189, 179, 132, 101, 197, 234, 180, 113, 2, 55, 37, 160, 118, 204, 206, 153, 80, 243, 119, 56, 118, 29, 24, 41, 117, 175, 76, 2, 17, 0, 0, 0, 13, 73, 67, 205, 159, 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