Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e52760ca9da1373ac9570593c1b261360180c0c857b485fa3fe2344dc741653e

Tx prefix hash: 20b7e8da13862e51cdde26878a82aa7ddd60987362da4dea1b78cde0e7a0613c
Tx public key: ef6d90bd96f0fe9cb50db2ab621cdfc04b7a189522bc6d430122851a8ae93bc8
Timestamp: 1711909844 Timestamp [UCT]: 2024-03-31 18:30:44 Age [y:d:h:m:s]: 01:221:10:41:58
Block: 990499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416935 RingCT/type: yes/0
Extra: 01ef6d90bd96f0fe9cb50db2ab621cdfc04b7a189522bc6d430122851a8ae93bc802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e9aa7cc67a96c36f822bba8c3b904a7229b6b4e7bc5033ccfacd37f77c9789d 0.600000000000 1450821 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": 990509, "vin": [ { "gen": { "height": 990499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e9aa7cc67a96c36f822bba8c3b904a7229b6b4e7bc5033ccfacd37f77c9789d" } } ], "extra": [ 1, 239, 109, 144, 189, 150, 240, 254, 156, 181, 13, 178, 171, 98, 28, 223, 192, 75, 122, 24, 149, 34, 188, 109, 67, 1, 34, 133, 26, 138, 233, 59, 200, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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