Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa2fc4c75fcbcc7dfe4b3865293fd849fdeb33f4c6a57302bdf90fababcc0f5

Tx prefix hash: 4ccf890675d07cbbee9a2ab0ace8c5a4cd54c777823f9fabaf3cbf8e9004a477
Tx public key: 0a4608bdeebba022e7731adb35a59c6611dd3fb2b34a85875dc0432637e77622
Timestamp: 1737184382 Timestamp [UCT]: 2025-01-18 07:13:02 Age [y:d:h:m:s]: 00:057:16:23:57
Block: 1199878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41006 RingCT/type: yes/0
Extra: 010a4608bdeebba022e7731adb35a59c6611dd3fb2b34a85875dc0432637e776220211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd35550734418d44d4c6aa6ab4f5a0d4a28168aae10f7d2b27e6c005b7324e7b 0.600000000000 1686513 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": 1199888, "vin": [ { "gen": { "height": 1199878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd35550734418d44d4c6aa6ab4f5a0d4a28168aae10f7d2b27e6c005b7324e7b" } } ], "extra": [ 1, 10, 70, 8, 189, 238, 187, 160, 34, 231, 115, 26, 219, 53, 165, 156, 102, 17, 221, 63, 178, 179, 74, 133, 135, 93, 192, 67, 38, 55, 231, 118, 34, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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