Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2cd32616fd73a51074abcd8773a6143329383043655876edb1b337dfc27adbc

Tx prefix hash: eef64b4d49b08156e1d99a583556363cd7cb1446bf00e8d3eae485b20e29b4af
Tx public key: 7d243c1bfd7fb52b4ca0e8003f69137fcbe88ef19c61ae9e3f53977add4e7181
Timestamp: 1705437324 Timestamp [UCT]: 2024-01-16 20:35:24 Age [y:d:h:m:s]: 01:304:08:42:59
Block: 936805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476352 RingCT/type: yes/0
Extra: 017d243c1bfd7fb52b4ca0e8003f69137fcbe88ef19c61ae9e3f53977add4e71810211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b819e0c2210bba11514be611039b5ae909c383684d776dc62b71a3fefc40354 0.600000000000 1394845 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": 936815, "vin": [ { "gen": { "height": 936805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b819e0c2210bba11514be611039b5ae909c383684d776dc62b71a3fefc40354" } } ], "extra": [ 1, 125, 36, 60, 27, 253, 127, 181, 43, 76, 160, 232, 0, 63, 105, 19, 127, 203, 232, 142, 241, 156, 97, 174, 158, 63, 83, 151, 122, 221, 78, 113, 129, 2, 17, 0, 0, 0, 1, 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