Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 877d42a5a5d8d3b3f670eee950af7d7ee654f6b31fe0cbb0cbe69bc2857b8826

Tx prefix hash: e42f7dc1ac0e86955c91acb41d331c2a7b14aee99d94a77131607a4503ca48bd
Tx public key: 40f37bbff844dbfc9eb4a9803421f487f9f4940edccb7ea69724e2e04b25c9e3
Timestamp: 1706694694 Timestamp [UCT]: 2024-01-31 09:51:34 Age [y:d:h:m:s]: 01:027:14:32:49
Block: 947231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280766 RingCT/type: yes/0
Extra: 0140f37bbff844dbfc9eb4a9803421f487f9f4940edccb7ea69724e2e04b25c9e302110000001a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d60f2c01d80ed1d5ff2aa5f12dd622c9cb636ba43233597551d9bfa07177b78 0.600000000000 1405579 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": 947241, "vin": [ { "gen": { "height": 947231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d60f2c01d80ed1d5ff2aa5f12dd622c9cb636ba43233597551d9bfa07177b78" } } ], "extra": [ 1, 64, 243, 123, 191, 248, 68, 219, 252, 158, 180, 169, 128, 52, 33, 244, 135, 249, 244, 148, 14, 220, 203, 126, 166, 151, 36, 226, 224, 75, 37, 201, 227, 2, 17, 0, 0, 0, 26, 89, 218, 211, 245, 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