Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2170d433286a7865925cc1f3947737b77951617100a56839b76049aa64a67bd5

Tx prefix hash: a55789ce3f5cf883885dcb06f31d881f817bada6977a83c7380cf9133851580c
Tx public key: 014e2861f7c44db56aa557272081f2f6ad3e4e079288918cb83d743c9af7b16a
Timestamp: 1698243239 Timestamp [UCT]: 2023-10-25 14:13:59 Age [y:d:h:m:s]: 01:159:16:39:36
Block: 877397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375117 RingCT/type: yes/0
Extra: 01014e2861f7c44db56aa557272081f2f6ad3e4e079288918cb83d743c9af7b16a021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.760010392000 dcy

stealth address amount amount idx
00: 73ec6184a1bd5a4988317556beca2641c9eba3df2fa4933c24488ea2af6f8f47 0.760010392000 1332771 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": 877407, "vin": [ { "gen": { "height": 877397 } } ], "vout": [ { "amount": 760010392, "target": { "key": "73ec6184a1bd5a4988317556beca2641c9eba3df2fa4933c24488ea2af6f8f47" } } ], "extra": [ 1, 1, 78, 40, 97, 247, 196, 77, 181, 106, 165, 87, 39, 32, 129, 242, 246, 173, 62, 78, 7, 146, 136, 145, 140, 184, 61, 116, 60, 154, 247, 177, 106, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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