Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28912afa4056da4528aadd11defc7a4750f6df9b6ae3aa5a2121eca6be015699

Tx prefix hash: da9cf6fb727d5f795370d3722fdc034c69f6e41f15efd14c6d1863f89b2c28a1
Tx public key: b25f6f83efd2f60d18a98cdea07cbf8fb47c62bccd0e3cf63d875da2b54c2f40
Timestamp: 1706956523 Timestamp [UCT]: 2024-02-03 10:35:23 Age [y:d:h:m:s]: 01:027:01:23:20
Block: 949398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280384 RingCT/type: yes/0
Extra: 01b25f6f83efd2f60d18a98cdea07cbf8fb47c62bccd0e3cf63d875da2b54c2f400211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8aa0b04cea2d76dfe66bfb5cdcfa72e84dddd9321c6bafd164bdf448cd9d28c2 0.600000000000 1407922 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": 949408, "vin": [ { "gen": { "height": 949398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aa0b04cea2d76dfe66bfb5cdcfa72e84dddd9321c6bafd164bdf448cd9d28c2" } } ], "extra": [ 1, 178, 95, 111, 131, 239, 210, 246, 13, 24, 169, 140, 222, 160, 124, 191, 143, 180, 124, 98, 188, 205, 14, 60, 246, 61, 135, 93, 162, 181, 76, 47, 64, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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