Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48dd137e1922f10f1bb7fc51f80ac03573f4d63a96a9709590e7d4dec80c0848

Tx prefix hash: f60da2f48d1f722b274c0affa9aa69e4ea1c1daf43a063f38b72205c8a21f4fe
Tx public key: 8739bfaf7f6f463bbd6fc09801ce6b6184cfbcc41d7f1df67fc060a805d18274
Timestamp: 1685478439 Timestamp [UCT]: 2023-05-30 20:27:19 Age [y:d:h:m:s]: 01:319:17:02:17
Block: 771609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489700 RingCT/type: yes/0
Extra: 018739bfaf7f6f463bbd6fc09801ce6b6184cfbcc41d7f1df67fc060a805d18274021100000003faf35c9c000000000000000000

1 output(s) for total of 1.703488650000 dcy

stealth address amount amount idx
00: 04e71d3a4c80a94d473cabd9fae1bec493648f34461251668c6ddf101e64767e 1.703488650000 1220982 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": 771619, "vin": [ { "gen": { "height": 771609 } } ], "vout": [ { "amount": 1703488650, "target": { "key": "04e71d3a4c80a94d473cabd9fae1bec493648f34461251668c6ddf101e64767e" } } ], "extra": [ 1, 135, 57, 191, 175, 127, 111, 70, 59, 189, 111, 192, 152, 1, 206, 107, 97, 132, 207, 188, 196, 29, 127, 29, 246, 127, 192, 96, 168, 5, 209, 130, 116, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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