Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25c5924f2c14f64772e6f396f76e66285f425eddf28e60bd8795cbebaffbf5c2

Tx prefix hash: 8b28c534a27c7b083ff510fdccbf2ca50cd3fe617e7957e2fc558496948ea6b9
Tx public key: 1a66fde6ed43aed23dc733131ab72bc323b6b7d40b604da1ce87564ce4f6f336
Timestamp: 1578906024 Timestamp [UCT]: 2020-01-13 09:00:24 Age [y:d:h:m:s]: 04:353:14:05:15
Block: 44455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1142299 RingCT/type: yes/0
Extra: 011a66fde6ed43aed23dc733131ab72bc323b6b7d40b604da1ce87564ce4f6f336021100000b20391a8d0e000000000000000000

1 output(s) for total of 437.222971945000 dcy

stealth address amount amount idx
00: a4d0cc521911d9c107e944f9a5ddc82e82ea246a2eaef0a840d585d0ff192612 437.222971945000 80907 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": 44465, "vin": [ { "gen": { "height": 44455 } } ], "vout": [ { "amount": 437222971945, "target": { "key": "a4d0cc521911d9c107e944f9a5ddc82e82ea246a2eaef0a840d585d0ff192612" } } ], "extra": [ 1, 26, 102, 253, 230, 237, 67, 174, 210, 61, 199, 51, 19, 26, 183, 43, 195, 35, 182, 183, 212, 11, 96, 77, 161, 206, 135, 86, 76, 228, 246, 243, 54, 2, 17, 0, 0, 11, 32, 57, 26, 141, 14, 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