Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29e8e5960340edb97125db14819aa617f30fa9a9a9c26d79137fed4c0d7c79bf

Tx prefix hash: 1f4735f2f6a40bf9c171b19320b9396f6df67f82ffbd45fc5d0ebfa6bfd848df
Tx public key: 311b89375c1c75452569b960a8eb21b6dbe3a53c5a0a19d871131516ba465db7
Timestamp: 1727832528 Timestamp [UCT]: 2024-10-02 01:28:48 Age [y:d:h:m:s]: 00:054:02:01:59
Block: 1122501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38634 RingCT/type: yes/0
Extra: 01311b89375c1c75452569b960a8eb21b6dbe3a53c5a0a19d871131516ba465db7021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4df74e249ea1bb8fd82368b795a07ed417f9c07197ad7e2b1ad05d6f98579f9 0.600000000000 1604952 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": 1122511, "vin": [ { "gen": { "height": 1122501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4df74e249ea1bb8fd82368b795a07ed417f9c07197ad7e2b1ad05d6f98579f9" } } ], "extra": [ 1, 49, 27, 137, 55, 92, 28, 117, 69, 37, 105, 185, 96, 168, 235, 33, 182, 219, 227, 165, 60, 90, 10, 25, 216, 113, 19, 21, 22, 186, 70, 93, 183, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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