Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3425ee26dfe59194e4c5a5914f4d9906bab9ada8fa9194aa0173c7517ec60c47

Tx prefix hash: 25466d3b0efda4b3afb61e6f7e5ca9d6355987576ea17d1ce0d6a8db575aa6ac
Tx public key: c39c8c3008655ed5bdf10a2540f46cee92f6da0339a85950e0189b9116c79c9d
Timestamp: 1698481025 Timestamp [UCT]: 2023-10-28 08:17:05 Age [y:d:h:m:s]: 01:164:10:16:31
Block: 879378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378500 RingCT/type: yes/0
Extra: 01c39c8c3008655ed5bdf10a2540f46cee92f6da0339a85950e0189b9116c79c9d02110000000433af99f4000000000000000000

1 output(s) for total of 0.756400049000 dcy

stealth address amount amount idx
00: ae94d452703b0be69289addfed8b8b422c368dfd767ad92a5809d3165bd33967 0.756400049000 1334888 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": 879388, "vin": [ { "gen": { "height": 879378 } } ], "vout": [ { "amount": 756400049, "target": { "key": "ae94d452703b0be69289addfed8b8b422c368dfd767ad92a5809d3165bd33967" } } ], "extra": [ 1, 195, 156, 140, 48, 8, 101, 94, 213, 189, 241, 10, 37, 64, 244, 108, 238, 146, 246, 218, 3, 57, 168, 89, 80, 224, 24, 155, 145, 22, 199, 156, 157, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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